EMV tags are persisted by Portico and can be edited prior to the transaction being settled. This allows for the conversational nature of interfacing with a chip card using an EMV capable terminal. For example, the following is a general flow of an EMV conversation to complete a CreditSale transaction. For other flows, see the EMV section of the sample SoapUI project that is included in the SDK.
EMV Conversation Flow | ||||
1. |
Client interfaces with the EMV terminal and initiates a conversation with the chip card. The result of this conversation includes obtaining credit authorization EMV tags for the request. Portico is not involved in this conversation between the client and the terminal. | |||
2. |
Client initiates a Portico CreditSale request with Track 2 and EMV tag data. An error will be generated if EMV tag data is not accompanied by Track data. | |||
3. |
Portico initiates a request with the Heartland authorization system which includes the Tag Length Value (TLV) fields passed in by the client:
| |||
4. |
Client passes the issuer response tags to the EMV chip card/ terminal and receives the result from the chip card/terminal. | |||
5. |
If the EMV chip card/terminal accepts the transaction:
| |||
6. |
If the EMV chip card/terminal declines:
|